www.bandedbirds.org; Shorebird Resighting Database: Resighting Data Extraction

Metadata:

Frequently anticipated questions:


What does this data set describe?

Title:
www.bandedbirds.org; Shorebird Resighting Database: Resighting Data Extraction
Abstract:
Since 2003, New Jersey and Delaware Divisions of Fish and Wildlife and NJ Audubon Society have captured and individually marked over 35,000 red knots, ruddy turnstones, sanderlings and semipalmated sandpipers with coded leg flags during spring migration stopovers in Delaware Bay. Banders in Argentina have utilized engraved markers for red knot since 2001. These markers are conspicuous to observers at a distance, which allows identification of individual birds. Internationally, many additional banding programs have implemented this practice of marking based on the success of resighting efforts. The aforementioned organizations initiated the developement of a website and web-based relational database, www.bandedbirds.org, that allows field observers to report resightings of these uniquely marked shorebirds via the web. The relational database maintains both capture data and resighting data. Large quantities of banding and resighting data can be formatted in Excel in a fashion similar to field collection sheets for bulk uploads. Custom programming creates and maintains the relationship of capture and resighting data, even when band changes are made to an individual, allowing the retrieval of data that details a bird’s recorded history.
Supplemental_Information:
Several research groups contribute data to the Shorebird Resighting Database. Data is stored on a secure server and is archived daily. Downloads of secure data are available to approved researchers. Look-ups for an individual bird's history for personal use only is available to the general public.
  1. How should this data set be cited?

    Multiple authors for several projects participating in the overall database. Refer to the "Other Citation Details" section for specifics and proper publication credit., 20090501, www.bandedbirds.org; Shorebird Resighting Database: Resighting Data Extraction:, <http://www.bandedbirds.org>.

    Online Links:

    Other_Citation_Details:
    Publication Credit: Any form of publication using this data should credit: www.bandedbirds.org. In addition, each project contributing data to the dataset used should be individually credited. Please consult the metadata for each project for the correct citation(s). If metadata is not available, contact the database administrator for further information.

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -166.0090
    East_Bounding_Coordinate: -53.92750
    North_Bounding_Coordinate: 70.27835
    South_Bounding_Coordinate: -52.57645
    Description_of_Geographic_Extent:
    While the majority of the data comes from the Eastern Coasts of North and South America, some data has been received from the Western shorelines, as well.

  3. What does it look like?

  4. Does the data set describe conditions during a particular time period?

    Beginning_Date: Unknown
    Ending_Date: Unknown
    Currentness_Reference: ground condition

  5. What is the general form of this data set?

    Geospatial_Data_Presentation_Form: database; spreadsheet

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

      Indirect_Spatial_Reference:
      All resighting locations are identified by place. A code for a place relates to a table with a location name, generalized coordinates for the location area, state/province and country for that location.
      This is a Point data set.

    2. What coordinate system is used to represent geographic features?

      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 0.000001. Longitudes are given to the nearest 0.000001. Latitude and longitude values are specified in Decimal degrees.

      The horizontal datum used is World Geodetic System of 1984.
      The ellipsoid used is World Geodetic System of 1984.
      The semi-major axis of the ellipsoid used is 6378137.
      The flattening of the ellipsoid used is 1/298.25722210088.

  7. How does the data set describe geographic features?

    Resighting Data
    Location and individualized markers for observed birds. (Source: Producer defined.)

    Project
    The ID representing the group responsible for collecting resighting data and considered the owner of the data. (Source: none)

    ValueDefinition
    Refer to the document Metadata Resighting Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    Resight Date
    Date of observation. (Source: none)

    Range of values
    Minimum:none
    Maximum:none

    Country
    Country where bird was observed. (Source: none)

    ValueDefinition
    Country names are standardized in database reference table. 

    State/Province
    State or province where bird was observed. (Source: none)

    ValueDefinition
    State/Province names are standardized in database reference table. 

    Location
    Alphanumeric code to define the generalized geographic area of where the bird was observed. (Source: none)

    ValueDefinition
    Refer to the document Metadata Location Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    Latitude
    Latitude of location in decimal degrees where bird was observed. (Source: none)

    Range of values
    Minimum:-90
    Maximum:90

    Longitude
    Longitude in decimal degrees where bird was observed. (Source: none)

    Range of values
    Minimum:-180
    Maximum:180

    Observer First
    First name of the observer (Source: none)

    Free-form text.

    Observer Last
    Last name of the observer. (Source: none)

    Free-form text.

    Observer Email
    Email of the observer. (Source: none)

    Free-form text.

    Comments
    Comments regarding the overall scan condititions or events. (Source: none)

    Free-form text.

    Start Time
    Time scan (observation period) started in 24 hour time. Must be formatted with colons as per Microsoft protocol. (Source: none)

    Range of values
    Minimum:00:00
    Maximum:11:59
    Units:24 hour time

    End Time
    Time scan (observation period) started in 24 hour time. Must be formatted with colons as per Microsoft protocol. (Source: none)

    Range of values
    Minimum:00:00
    Maximum:11:59
    Units:24 hour time

    Tide
    Codes representing the stage of tide during the time of observation. (Source: none)

    ValueDefinition
    Refer to the document Metadata Resighting Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    Sky Overcast
    Cloud cover percentage. (Source: none)

    Range of values
    Minimum:0
    Maximum:100
    Units:whole numbers

    Beaufort
    Code representing force of wind. (Source: none)

    ValueDefinition
    Refer to the document Metadata Resighting Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    Visibility
    Code denoting the quality of the visibility conditions. (Source: none)

    ValueDefinition
    Refer to the document Metadata Resighting Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    Rain
    Codes denoting rainfall conditions. (Source: none)

    ValueDefinition
    Refer to the document Metadata Resighting Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    Surf
    Code denoting the degree of surf. (Source: none)

    ValueDefinition
    Refer to the document Metadata Resighting Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    Scan Quality
    Codes denoting the overall quality of the scan. (Source: none)

    ValueDefinition
    Refer to the document Metadata Resighting Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    Flock Activity
    Code denoting predominate flock activity. (Source: none)

    ValueDefinition
    Refer to the document Metadata Resighting Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    Human Activity
    Codes denoting predominate human activity impacting flock. (Source: none)

    ValueDefinition
    Refer to the document Metadata Resighting Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    User Defined
    Established resighting projects have the option to record data for user defined fields. This column contains the concatenation of field name(s) and data. (Source: defined by individual projects.)

    Projects may define any number of unique fields to house data specific to their research needs. Please see metadata for the specific project for definition of the field contents.

    Flocks
    Concatenation of the flock counts associated with the scan. Format is Species Code:# . Just flock counts in Excel format can be requested from the administrator. (Source: Species codes used are derived from "The North American Bird Banding Manual (electronic version)".)

    Any number of species counts can be recorded with the scan data. Species codes must conform to the species table, but the numbers of birds is not delimited.

    BirdID
    Unique number identifying an individual. (Source: none)

    Range of values
    Minimum:9401
    Maximum:ongoing

    Species
    Code representing the species of the bird. (Source: Derived from "The North American Bird Banding Manual (electronic version)".)

    ValueDefinition
    Refer to the document Metadata Resighting Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    Flag Color
    Code representing type of marker used as part of sequence to uniquely mark a bird. Marker present on observed bird. (Source: none)

    ValueDefinition
    Refer to the document Metadata Resighting Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    Flag Code
    Engraved code on marker or unique color sequence marking bird as an individual. (Source: none)

    Engraved codes or letter sequences based on color band sequences.

    Upper Left
    Colors observed on upper left leg. Colors are read top down for leg part. (Source: none)

    Free-form text.

    Lower Left
    Colors observed on lower left leg. Colors are read top down for leg part. (Source: none)

    Free-form text.

    Upper Right
    Colors observed on upper right leg. Colors are read top down for leg part. (Source: none)

    Free-form text.

    Lower Right
    Colors observed on lower right leg. Colors are read top down for leg part. (Source: none)

    Free-form text.

    Resight Certainty
    Degree of certainty by observer that report is accurate. (Source: none)

    Free-form text.

    Individual Comments
    Comments reserved for describing conditions about the individual bird. (Source: none)

    Free-form text.

    Entity_and_Attribute_Overview:
    Banding Data: The amount of biometric banding data maintained in this database is at the discretion of each participating research project. Each record will include at a minimum Project, Method, Capture Date, Country, State/Province, Location, Latitude, Longitude, BirdID, Species, Metal Out. All birds color marked as individuals will include Flag Color Out and Flag Code Out.
    Entity_and_Attribute_Detail_Citation: none

  8. What biological taxa does this data set concern?

    Taxonomy:
    Keywords/Taxon:
    Taxonomic_Keyword_Thesaurus: None
    Taxonomic_Keywords: multiple species
    Taxonomic_Keywords: birds
    Taxonomic_Keywords: shorebirds
    Taxonomic_Keywords: black-bellied plover
    Taxonomic_Keywords: Pluvialis squatarola
    Taxonomic_Keywords: dunlin
    Taxonomic_Keywords: Calidris alpina
    Taxonomic_Keywords: long-billed dowitcher
    Taxonomic_Keywords: Limnodromus scolopaceus
    Taxonomic_Keywords: least sandpiper
    Taxonomic_Keywords: Calidris minutilla
    Taxonomic_Keywords: Hudsonian godwit
    Taxonomic_Keywords: Limosa haemastica
    Taxonomic_Keywords: red knot
    Taxonomic_Keywords: Calidris canutus
    Taxonomic_Keywords: ruddy turnstone
    Taxonomic_Keywords: Arenaria interpres
    Taxonomic_Keywords: semipalmated sandpiper
    Taxonomic_Keywords: Calidris pusilla
    Taxonomic_Keywords: short-billed dowitcher
    Taxonomic_Keywords: Limnodromus griseus
    Taxonomic_Keywords: whimbrel
    Taxonomic_Keywords: Numenius phaeopus
    Taxonomic_System:
    Classification_System/Authority:
    Classification_System_Citation:
    Citation_Information:
    Originator: American Ornithologists' Union
    Publication_Date: 1998
    Title: Check-list of North American Birds
    Edition: Seventh
    Geospatial_Data_Presentation_Form: book, pdf
    Online_Linkage: <http://www.aou.org/checklist/north/>
    Classification_System_Modifications:
    Annual revisions by the American Ornithologists' Union are published in The Auk.
    Taxonomic_Procedures: Researchers have existing knowledge of bird identification.
    Taxonomic_Classification:
    Taxon_Rank_Name: Kingdom
    Taxon_Rank_Value: Animalia
    Applicable_Common_Name: animals
    Taxonomic_Classification:
    Taxon_Rank_Name: Phylum
    Taxon_Rank_Value: Chordata
    Applicable_Common_Name: chordates
    Taxonomic_Classification:
    Taxon_Rank_Name: Subphylum
    Taxon_Rank_Value: Vertebrata
    Applicable_Common_Name: vertebrates
    Taxonomic_Classification:
    Taxon_Rank_Name: Class
    Taxon_Rank_Value: Aves
    Applicable_Common_Name: birds
    Taxonomic_Classification:
    Taxon_Rank_Name: Order
    Taxon_Rank_Value: Charadriiformes


Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

  2. Who also contributed to the data set?

    Sponsors for the creation and maintenance of the website and database: Clear into the Future: a DuPont Delaware Estuary Initiative, Conserve Wildlife Foundation of New Jersey, New Jersey Audubon Society, New Jersey Division of Fish and Wildlife, Delaware Division of Fish and Wildlife, U.S. Fish & Wildlife Service.

  3. To whom should users address questions about the data?

    Jeannine Parvin
    New Jersey Audubon Society: Research Dept.
    Database Administrator
    600 Route 47 North
    Cape May Court House, NJ 08210
    USA

    609-465-3056 (voice)
    bandedbirds@comcast.net

    Contact_Instructions: Best source of contact is email.


Why was the data set created?

Resightings of marked birds allow researchers to estimate adult survival, stopover duration and population size as well as examine patterns of migratory movement and timing. Survival is a critical metric to monitor trend and assess health of migratory shorebird populations. Maintenance of banding and resighting in relational database allows provision of data to meet researchers' analytical needs utilizing specialized queries.


How was the data set created?

  1. What methods were used to collect the data?

    Method 0 of 1
    Type: Field

    Birds are observed in the field. Most resightings are determined through the use of a spotting scope. Some observers are able to report using binoculars. Reports are also submitted based on photography and videography.

  2. From what previous works were the data drawn?

    (source 1 of 1)
    Multiple authors for several projects participating in the overall database., Unknown.

    Type_of_Source_Media: field notes
    Source_Contribution:
    Resighting data is collected from both research organizations/projects and from the general public via the website entry form. With a few exceptions, all observations include the observer's name and email.
    A complete list of formal resighting projects can be found within the metadata section at <http://report.bandedbirds.org/>. Additionally, metadata for each project will be posted at this site as it becomes available.

  3. How were the data generated, processed, and modified?

    Date: May-2009 (process 1 of 1)
    The database and associated website went live May 1, 2009. All data collected since that date have been formatted according to database requirements.

    Person who carried out this activity:

    Jeannine Parvin

    bandedbirds@comcast.net

  4. What similar or related data should the user be aware of?

    Multiple authors for several projects participating in the overall database., 20090501, Shorebird Resighting Database: Resighting Data Extraction:, <http://www.bandedbirds.org>.

    Online Links:

    Other_Citation_Details:
    Related resightings to the banding data in the Shorebird Resighting Database.


How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?

    Accuracy for resighting data submitted for an organized effort is the responsibility of the submitting organization. However, all resighting data is proofed by the database administrator, as well, to provide additional error-checking. Any inaccuracies observed, other than obvious data entry errors, are reported to the submitting organization for correction.
    All resightings submitted by the public via the website reporting form are reviewed by the database administrator. Inaccurate data is cleared as much as possible by communicating with the observer.
    Specifically, the administrator checks for consistency of coordinates for stated location and adherence to character set for flagging codes. Many attributes are related to a look-up table. The upload programming only allows correct attribute codes. If incorrect codes are detected, the upload process ends and an error report is issued.
    It should be noted that with the data based on personal field observation, sometimes inaccurate flag codes are reported. These are not necessarily corrected. Most researchers want to work with "true" observations, not guesses at corrections. There is statiscal merit in determining the number of known "misreads" to calculate the veracity of the dataset as a whole.
    As the data is used in analytical study, errors come to light. Any changes made to the resighting data are logged in a report. This document is available for viewing/download by approved researchers.

  2. How accurate are the geographic locations?

    Latitude and longitude coordinates are required for each resighting location. The accuracy of the coordinates may vary based on the reporting method. Some projects select a set of coordinates representing an area within which trapping takes place and some pinpoint the coordinates for a catch using Google Earth or a GPS unit. Metadata for a specific project should be consulted to determine the specifics.
    Pubically submitted resightings also vary. Most observers take advantage of the Google Map feature that allows them to choose coordinates from the map. Some do submit coordinates based on GPS units.

  3. How accurate are the heights or depths?

  4. Where are the gaps in the data? What is missing?

    Submissions to the database via the website entry form are continuous. Numbers of submissions vary from approximately 10 per week to upwards of 50, dependent on the time of year. Publically submitted resightings are reviewed by the database administrator for validity. Once validated, they are available for download by approved researchers. This validation procedure is typically performed once a week. Note, however, all resightings are immediately available for viewing using the publically accessed "Map Your Resighting" feature. Until vetted by the administrator, this data will not include a place name, but will simply display the raw coordinates entered by the observer. This display of data cannot be considered completely accurate.
    Resighting data is also submitted in an upload format by projects conducting formalized resighting efforts. The database is updated as often as datasets are provided in the correct format. All participating resighting projects are submitting data regularly post-field season/expedition. The time lag from field work to submission of data varies by project, but all do submit within a few months of field work.
    There are still historic resighting not included in the database. Prior to the centralized database, resightings have been collected in various formats: spreadsheets, archived emails, written or typewritten submissions. While the majority of past work has been submitted, some projects still have uncollated data.

  5. How consistent are the relationships among the observations, including topology?


How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access_Constraints:
Direct access to bulk data is limited to approved researchers. Approval for access is granted by the participating project leaders. Researchers may also request specialized downloads via the database administrator, who will seek the requisite permission from the appropriate project leaders.
The general public may look-up an individual bird's history after registration and acceptance of a Terms of Use agreement.
Use_Constraints:
Approved research users must agree that they will not reproduce, communicate, or otherwise make available the content to which they are permitted access to third parties. Use constraints for special requests are individualized between a researcher requesting data and the projects supplying data. To begin the process, the researcher should contact the database administrator by email. The email should include a personal introduction, the data the researcher is interested in accessing and the anticipated use of the data. The public history available for viewing on the website is for personal use only.

  1. Who distributes the data set? (Distributor 1 of 1)

    Jeannine Parvin
    Database Administrator

    bandedbirds@comcast.net

    Contact_Instructions: contact via email
  2. What's the catalog number I need to order this data set?

  3. What legal disclaimers am I supposed to read?

    N/A

  4. How can I download or order the data?


Who wrote the metadata?

Dates:
Last modified: 10-Mar-2011
Metadata author:
Jeannine Parvin
Database Administrator

bandedbirds@comcast.net

Contact_Instructions: Best form of contact is email.
Metadata standard:
FGDC Biological Data Profile of the Content Standard for Digital Geospatial Metadata (FGDC-STD-001.1-1999)


Generated by mp version 2.9.13 on Thu Mar 17 16:32:58 2011